SAP Finance And Controlling (SAP FICO) Training Interview Qu...

SAP FICO is the finance and controlling module of SAP ERP/S4HANA, combining Financial Accounting (FI) for external/legal reporting with Controlling (CO) for internal cost management, budgeting and profitability analysis.

FI captures transactions for external, statutory financial reporting such as balance sheet and P&L, while CO is used for internal management reporting, cost tracking, and profitability analysis and is not legally mandated.

A Company Code is the smallest organizational unit for which a complete, independent set of accounts (balance sheet and P&L) can be drawn up for external reporting purposes.

A Chart of Accounts is the structured list of all G/L accounts used by one or more company codes, defining the account number, name, and control fields such as account group and account type.

Operating Chart of Accounts (used for daily postings, assigned to the company code), Country Chart of Accounts (for statutory reporting by country) and Group Chart of Accounts (for consolidated group reporting) are the three types.

A Controlling Area is the organizational unit within CO used to represent a closed system for cost accounting purposes, and can be assigned to one or more company codes for cross-company cost controlling.

A Fiscal Year Variant defines the number of posting periods in a fiscal year (normally 12 plus special periods) and whether the fiscal year is calendar-based or non-calendar, and is assigned to the company code.

A Posting Period Variant controls which posting periods are open or closed for posting, and can be shared across multiple company codes to standardize period control.

A Document Type (e.g. SA, KR, DR) classifies accounting documents, controls the number range used and restricts which account types (G/L, customer, vendor, asset) can be posted to.

A Posting Key is a two-digit code that determines whether a line item is a debit or credit, the account type it applies to, and the field status of the entry screen.

A Field Status Group, assigned to a G/L account, controls which fields are suppressed, optional, or mandatory during document entry for that account.

A Tolerance Group defines the permitted payment differences and amount limits for a user or account during clearing and posting, helping control acceptable variances.

A Reconciliation Account is a G/L account linked to a sub-ledger (customer, vendor or asset) that is automatically updated in real time whenever a posting is made in the sub-ledger, ensuring the G/L always reflects sub-ledger balances.

Open Item Management is a G/L account setting that keeps individual line items open until they are cleared against an offsetting entry, commonly used for bank clearing, GR/IR, and payable/receivable accounts.

A Clearing Document is the accounting document created when one or more open items are matched and offset against each other, marking them as cleared.

Partial Payment posts the incoming amount as a new open item while leaving the original invoice open for the remaining balance, whereas Residual Payment clears the original invoice completely and creates a new open item for the unpaid difference.

A House Bank represents a bank where the company holds an account, configured with bank keys, account IDs and linked G/L accounts used for payment and receipt transactions.

EBS processing imports the bank statement file, automatically matches transactions to open items using posting rules and algorithms, and posts the identified items to clear bank sub-accounts and update the main bank account.

Dunning is the automated process of sending reminder letters to customers for overdue open items, using dunning levels, procedures and letters configured to reflect escalating urgency.

Payment Terms define the due date calculation, cash discount days and percentages applicable to an invoice, and are assigned at the customer/vendor master or document level.

Withholding Tax is tax deducted at source on certain payments and is configured using withholding tax types (for invoice or payment) and withholding tax codes that define the rate and base amount, assigned to the vendor master.

A Tax Procedure defines the sequence of condition types used to calculate taxes such as VAT/GST, and is assigned to a country; tax codes within it determine the applicable rate and G/L account posting.

Automatic Account Determination uses configuration (e.g. transaction/event keys) to determine the correct G/L accounts for postings such as tax, cash discount, exchange rate differences and bank charges without manual entry.

Asset Accounting is the FI sub-module that manages the complete lifecycle of fixed assets, including acquisition, capitalization, depreciation, transfers and retirement, and keeps values for different accounting principles.

A Depreciation Area stores asset values calculated under a specific valuation approach or accounting principle (e.g. book depreciation, tax depreciation, IFRS), allowing parallel valuation of the same asset.

An Asset Class is the main classification criterion for assets, controlling the number range, screen layout and default account determination for assets created under it.

Classic Asset Accounting posts depreciation via periodic batch jobs and reconciles separately with G/L, while New Asset Accounting integrates directly with the ledger approach, supports parallel depreciation areas as separate ledgers, and posts in real time.

The Depreciation Run is a periodic batch job that calculates and posts planned depreciation, interest and other asset-related values to the G/L for all relevant assets in a company code.

Asset Capitalization is the process of transferring costs (e.g. from an Asset Under Construction or a purchase order) into a final asset master record, from which point depreciation begins.

AUC is a special asset class used to accumulate costs during a construction or development project before the asset is complete, after which the accumulated value is settled to the final asset(s).

A Cost Element is a CO master data object that categorizes costs and revenues; Primary Cost Elements correspond to a G/L account for external costs, while Secondary Cost Elements exist only in CO for internal allocations.

Primary Cost Elements originate from FI postings (must have a corresponding G/L account) and represent costs from outside CO, while Secondary Cost Elements are used purely within CO for internal allocations like assessment, distribution and settlement, with no G/L account.

A Cost Center is an organizational unit within a Controlling Area representing a location where costs are incurred, used to plan, collect and report on costs by responsibility area.

A Profit Center is an organizational unit used to analyze internal profit or loss for a business segment or product line, receiving revenue and cost postings for management reporting.

A Cost Center is used to track costs incurred by a department or function for responsibility accounting, while a Profit Center captures both costs and revenues to evaluate profitability of a business unit.

An Internal Order is a CO object used to plan, collect and monitor costs for a specific short-term task, event or project, and its costs are typically settled to a cost center, asset or G/L account at completion.

The typical lifecycle is creation, budgeting/planning, actual cost posting, periodic or final settlement to a receiver object, and closure/technical completion.

A Settlement Rule, maintained on an internal order or WBS element, defines the receiver object(s) and percentage/amount to which accumulated costs should be transferred during settlement.

A Work Breakdown Structure element is a component of a project in SAP PS used to structure and collect planned and actual costs, integrating with FI and CO for budgeting, commitment and settlement.

Commitment Management tracks committed (not yet actual) costs, such as open purchase orders or purchase requisitions, against a cost object's budget, giving visibility into future obligations before invoicing.

Availability Control monitors actual and committed costs against the budget assigned to a cost object (like an internal order or WBS element), triggering warnings or blocking further postings when defined tolerance thresholds are exceeded.

An Activity Type represents a measurable service or output produced by a cost center (e.g. machine hours, labor hours), used as the basis for allocating costs to other cost objects.

A Statistical Key Figure is a non-monetary measure (e.g. headcount, square footage) used as the basis for allocating costs proportionally between cost centers during assessment or distribution cycles.

Distribution allocates costs using the original (primary) cost element, preserving cost element detail at the receiver, while Assessment summarizes costs under a secondary cost element, losing the original cost element breakdown but simplifying reporting.

An Allocation Cycle is a set of rules defining senders, receivers, and the basis (percentages, SKFs, or fixed amounts) used to periodically distribute or assess costs between cost objects.

Overhead Cost Controlling manages indirect costs that cannot be directly attributed to a product, using cost centers, internal orders, and allocation cycles to assign these costs appropriately for analysis and product costing.

Product Costing calculates the planned and actual cost of manufacturing a product, using a cost estimate built from the BOM, routing and overhead rates, and supports both standard and actual costing approaches.

Standard Costing uses a predetermined cost calculated in advance for valuation throughout the period, while Actual Costing (using Material Ledger) recalculates the true incurred cost of a material at period end, capturing variances.

Cost Component Split breaks the total cost of a manufactured product into components such as raw material, labor, machine and overhead, giving visibility into cost structure for analysis and pricing decisions.

Variance Calculation compares the target cost (based on standard) with the actual cost incurred on a production or process order, categorizing differences into variance types such as price, quantity, and scrap variance.

WIP calculation values partially completed production orders at period end by capturing costs incurred that have not yet been settled as finished goods, ensuring accurate period-end inventory and P&L reporting.

Settlement transfers the calculated variances or WIP from a production/process order to the relevant receiver, typically the material (as price difference) or the G/L (as WIP), closing out the cost object for the period.

CO-PA is a CO component that analyzes an organization's profit or loss by market segments such as customer, product, region, or sales organization, providing multidimensional profitability reporting.

Account-Based CO-PA uses the standard G/L cost and revenue elements and always reconciles with FI, while Costing-Based CO-PA uses value fields and its own costing logic, offering more flexible reporting but requiring separate reconciliation with FI.

A Value Field in Costing-Based CO-PA stores amounts such as revenue, discounts, or cost of goods sold that are populated during billing or other postings for profitability reporting.

Derivation is the process by which CO-PA automatically determines characteristic values (such as customer group or region) based on rules and existing data during a posting, without manual entry.

Top-Down Distribution takes an aggregated value (such as a planned or adjusted figure) and distributes it proportionally down to detailed market segment combinations based on a reference structure.

Real-Time FI-CO Integration automatically and immediately posts a corresponding CO document whenever an FI posting affects a CO object (like a cost center or profit center), eliminating the need for periodic reconciliation.

The Reconciliation Ledger was used in classic ECC to periodically reconcile CO postings back to FI when real-time integration was insufficient; it is obsolete in S/4HANA since the Universal Journal keeps FI and CO permanently reconciled.

The Universal Journal is a single line-item table (ACDOCA) in S/4HANA that merges FI, CO, Asset Accounting, and Material Ledger data, providing one source of truth and eliminating reconciliation between modules.

Document Splitting is a New GL/S/4HANA feature that automatically splits accounting line items (e.g. vendor invoice) so that each document is balanced by dimensions such as profit center or segment, enabling entity-level financial statements.

The Leading Ledger reflects the accounting principle used for the company's primary/consolidated financial statements and is updated by all business transactions, while Non-Leading Ledgers represent alternative accounting principles (e.g. local GAAP) and can have different fiscal year variants or posting periods.

Parallel Accounting is the ability to maintain financial values simultaneously under multiple accounting principles (e.g. IFRS and local GAAP) using leading and non-leading ledgers or parallel accounts/valuation approaches.

Special Purpose Ledger is a flexible reporting tool used to collect and summarize data from various SAP modules for custom reporting needs not covered by standard ledgers; largely superseded in S/4HANA by the Universal Journal.

Foreign Currency Valuation is a period-end process that revalues open items and G/L balances held in foreign currency using current exchange rates, posting the resulting exchange rate differences to designated accounts.

SAP supports up to three parallel currencies per company code (transaction, company code/local, and group currency), stored simultaneously with each line item and converted using configured exchange rate types.

Typical activities include the depreciation run, accrual and provision postings, foreign currency valuation, GR/IR clearing, balance carryforward, and generation of financial statements.

Balance Carryforward is the process that transfers year-end G/L, customer, vendor and asset balances into the new fiscal year as opening balances, run typically at the start of a new fiscal year.

A Provision is a liability of uncertain timing or amount recognized based on a probable obligation, while an Accrual recognizes a known expense in the period it is incurred even though the invoice has not yet been received.

Validation checks that entered data meets defined business rules and blocks or warns on invalid postings, while Substitution automatically replaces or fills field values (such as profit center) during document entry based on defined rules.

Posting periods are opened or closed using transaction OB52, which defines the allowed period intervals per account type (G/L, customer, vendor, asset) and posting period variant.

Intercompany Reconciliation is the process of matching and resolving balances between transactions posted across different company codes within the same corporate group to ensure consolidated accounts are accurate.

A Segment is a reporting dimension in New GL, often used for IFRS 8 segment reporting, that can be automatically derived and used with document splitting to produce segment-level financial statements.

Lockbox is an automated process where customer payments received at a bank lockbox facility are electronically imported into SAP and automatically matched and cleared against open customer invoices.

The GR/IR account temporarily holds the value of goods received but not yet invoiced (or vice versa); mismatches are resolved by analyzing open GR/IR line items, correcting quantity/price discrepancies, and running periodic GR/IR clearing/maintenance reports.

MM integrates with FI through automatic account determination (OBYC) during goods movements and invoice verification, posting inventory, GR/IR, and price difference entries to the G/L in real time.

SD integrates with FI/CO through billing document postings that update revenue, cost of goods sold and receivables accounts, and simultaneously post to CO-PA for profitability analysis via pricing condition-to-value-field mapping.

Pricing Conditions in the sales document determine values like net price, discounts, freight and tax that are mapped to specific G/L accounts and CO-PA value fields through account determination during billing.

The Authorization Concept controls which users can execute specific FI/CO transactions and access specific data (e.g. company codes, cost centers), implemented through roles, authorization objects and profiles maintained via PFCG.

Segregation of Duties ensures no single user has conflicting authorizations (e.g. creating a vendor and also approving its payment), reducing fraud risk and supporting audit and compliance requirements.

Master data governance is handled through approval workflows for creating/changing G/L accounts, cost centers, and vendor/customer masters, along with validation rules and periodic data quality reviews.

Migration involves technical conversion of the database and data model to the simplified S/4HANA structure (e.g. ACDOCA), adapting custom code, reconciling FI and CO balances, and adopting new functionality like New Asset Accounting and Universal Journal.

Common challenges include historical data volume and consistency, custom code adaptation for obsolete tables, reconciling legacy CO and FI balances, and redesigning processes to leverage document splitting and real-time integration.

Central Finance is an S/4HANA deployment option that replicates financial transactions from one or more source ERP systems (SAP or non-SAP) into a central S/4HANA system in near real time for harmonized group reporting without a full technical migration.

New Asset Accounting integrates directly with the ledger approach, treating each depreciation area/accounting principle combination almost like its own ledger, enabling parallel valuation and real-time posting without periodic reconciliation runs.

Cash Management provides visibility into liquidity by consolidating bank account balances and cash positions, while Bank Account Management centrally maintains and controls bank account master data and related authorizations.

FB50 is used to post a G/L account document (general journal entry) directly, allowing multiple debit and credit line items in a single-screen entry transaction.

F-28 is used to post an incoming customer payment against open receivables, while F-53 is used to post an outgoing vendor payment against open payables, both allowing manual open item clearing.

FBL1N displays vendor line items, FBL3N displays G/L account line items, and FBL5N displays customer line items, each supporting open, cleared, or all items display for account analysis.

F110 is the Automatic Payment Program used to process outgoing (or incoming) payments in bulk, selecting due open items, applying payment methods, and generating payment media such as bank transfers or checks.

KSU5 executes an Assessment cycle and KSV5 executes a Distribution cycle, allocating costs from sender cost centers to receiver cost objects based on the configured cycle segments.

CO-PA reconciliation is the process of ensuring revenue and cost values captured in Costing-Based CO-PA match the corresponding G/L postings in FI, typically done through periodic comparison reports since costing-based CO-PA is not automatically synchronized.

A Ledger Group is a combination of one or more ledgers that can be posted to together, allowing documents to be restricted to specific ledgers (e.g. only the non-leading ledger) for accounting-principle-specific postings such as depreciation adjustments.

A Chart of Depreciation is a country-specific template containing the depreciation areas and valuation rules available for asset accounting, assigned to one or more company codes within that country.

A G/L Account Group controls the number range for G/L account creation and determines the field status (which fields are displayed/required) on the account master record.

Cost Center Category classifies cost centers by function (e.g. production, administration, sales) and can control which types of postings (like revenue) are permitted on that cost center.

An Order Type controls the number range, field selection, budgeting profile, and settlement profile applicable to internal orders created under it, differentiating types such as overhead orders or investment orders.

A Budget Profile, assigned to an internal order or WBS element, controls parameters for budgeting such as tolerance limits, availability control activation, and whether annual or overall budgeting is used.

A Settlement Profile defines the valid receiver categories, allocation structure, and default settlement rules that control how a cost object (like an internal order) can be settled.

An Allocation Structure groups cost elements into settlement assignments that determine which secondary cost element is used when settling costs from a sender object to a receiver during settlement.

A Results Analysis key is used to calculate Work in Process or reserves for unrealized costs on cost objects like sales orders or production orders during period-end processing, prior to final settlement.

Material Ledger is the technical infrastructure that stores material values in multiple currencies and valuation views, and Actual Costing is a specific process within Material Ledger that revalues materials at period end based on actual costs incurred, including variances.

PCA configuration involves defining profit centers, assigning them to master data (materials, cost centers) so that revenue and costs are attributed automatically, and activating the profit center update within the controlling area.

A Derivation Rule (or default assignment) determines which profit center a transaction is posted to when it is not directly available, based on criteria such as material, cost center, or sales area.

Controlling Area Currency is the currency in which CO objects like cost centers primarily store values; it can be the same as, or different from, individual company code currencies, and cross-company controlling requires careful currency configuration.